Method and apparatus for processing data for packet duplication

ABSTRACT

The present disclosure relates to a communication technique that fuses IoT technology with a 5G communication system to support a higher data transfer rate than a 4G communication system, and a system therefor. The present disclosure may be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, health care, digital education, retailing, security and safety related services, etc.) on the basis of 5G communication technology and IoT related technology. The present disclosure relates to a 5G or pre-5G communication system for supporting a higher data transmission rate than a 4G communication system such as LTE. An embodiment of the present invention relates to a method and a structure for processing data for packet duplication. According to the embodiment of the present invention, disclosed are a radio bearer setup method, a packet duplication operation, and a buffer status reporting method, which are for use in performing packet duplication.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/496,940 filed on Sep. 23, 2019, which is a 371 of InternationalApplication No. PCT/KR2018/002264 filed on Feb. 23, 2018, which claimspriority to Korean Patent Application No. 10-2017-0036822 filed on Mar.23, 2017, Korean Patent Application No. 10-2017-0075075 filed on Jun.14, 2017, and Korean Patent Application No. 10-2017-0126578 filed onSep. 28, 2017, the disclosures of which are herein incorporated byreference in their entirety.

BACKGROUND 1. Field

The disclosure relates to a method and an apparatus for processing datafor packet duplication and, more particularly to, a data structure forpacket duplication.

2. Description of Related Art

In order to meet wireless data traffic demands that have increased after4G communication system commercialization, efforts to develop animproved 5G communication system or a pre-5G communication system havebeen made. For this reason, the 5G communication system or the pre-5Gcommunication system is called a beyond 4G network communication systemor a post-LTE system.

In order to achieve a high data transmission rate, an implementation ofthe 5G communication system in a mmWave band (for example, 60 GHz band)is being considered. In the 5G communication system, technologies suchas beamforming, massive MIMO, Full Dimensional MIMO (FD-MIMO), arrayantenna, analog beam-forming, and large scale antenna are beingdiscussed as means to mitigate a propagation path loss in the mmWaveband and increase a propagation transmission distance.

Further, the 5G communication system has developed technologies such asan evolved small cell, an advanced small cell, a cloud Radio AccessNetwork (RAN), an ultra-dense network, Device to Device communication(D2D), a wireless backhaul, a moving network, cooperative communication,Coordinated Multi-Points (CoMP), and received interference cancellationto improve the system network.

In addition, the 5G system has developed Advanced Coding Modulation(ACM) schemes such as Hybrid FSK and QAM Modulation (FQAM) and SlidingWindow Superposition Coding (SWSC), and advanced access technologiessuch as Filter Bank Multi Carrier (FBMC), Non Orthogonal Multiple Access(NOMA), and Sparse Code Multiple Access (SCMA).

Meanwhile, the Internet has been evolved from a human-orientedconnection network in which humans generate and consume information, toan Internet of Things (IoT) network in which distributed componentsincluding things exchange and process information. An Internet ofEverything (IoE) technology in which a big data processing technologythrough a connection with a cloud server or the like is combined withthe IoT technology has emerged. In order to implement IoT, technicalfactors such as a sensing technique, wired/wireless communication,network infrastructure, service-interface technology, and securitytechnology are required, and research on technologies such as a sensornetwork, Machine-to-Machine (M2M) communication, Machine-TypeCommunication (MTC), and the like for connection between objects hasrecently been conducted. In an IoT environment, through collection andanalysis of data generated in connected objects, an intelligent InternetTechnology (IT) service to create a new value for peoples' lives may beprovided. The IoT may be applied to fields such as smart homes, smartbuildings, smart cities, smart cars, connected cars, smart grids, healthcare, smart home appliances, or high-tech medical services through theconvergence of the conventional Information Technology (IT) and variousindustries.

Accordingly, various attempts to apply the 5G communication system tothe IoT network are being made. For example, 5G communicationtechnologies, such as a sensor network, machine to machine (M2M)communication, machine type communication (MTC), and the like areimplemented by technologies, such as beam forming, MIMO, and an arrayantenna. The application of a cloud RAN as the big data processingtechnology may be an example of convergence of the 5G technology and theIoT technology.

Meanwhile, in a packet-based mobile communication system, research on amethod and a structure for processing data for packet duplication isrequired.

SUMMARY

A technical problem to be solved by an embodiment of the disclosure isto provide a method and apparatus for processing data for packetduplication and, more particularly to provide a data structure therefor.

A technical problem to be solved by the disclosure is to provide a radiobearer configuration scheme, a packet duplication operation, and abuffer status reporting scheme when performing packet duplication.

According to an embodiment of the disclosure, a method of a terminal ina mobile communication system may include: receiving, from a basestation, information for mapping a logical channel to a componentcarrier (CC); and transmitting data packet processed in the logicalchannel, to the base station through the CC to which the logical channelhas been mapped according to the information.

According to another embodiment of the disclosure, a terminal in amobile communication system may include: a transceiver for transmittingor receiving a signal; and a controller configured to receive, from abase station, information for mapping a logical channel to a componentcarrier (CC), and transmit a data packet processed in the logicalchannel, to the base station through the CC to which the logical channelhas been mapped according to the information.

According to still another embodiment of the disclosure, a method of abase station in a mobile communication system may include: transmitting,to a terminal, information for mapping a logical channel to a componentcarrier (CC); and receiving a data packet processed in the logicalchannel, from the terminal through the CC to which the logical channelhas been mapped according to the information.

According to still another embodiment of the disclosure, a base stationin a mobile communication system may include: a transceiver fortransmitting or receiving a signal; and a controller configured totransmit, to a terminal, information for mapping a logical channel to acomponent carrier (CC), and receive a data packet processed in thelogical channel, from the terminal through the CC to which the logicalchannel has been mapped according to the information.

The technical problems to be solved by the disclosure are not limited tothe above mentioned technical subjects, and other technical subjectswhich are not mentioned herein may be clearly understood, through thefollowing descriptions, by those skilled in the art of the disclosure.

An embodiment of the disclosure may provide a data processing method andstructure for packet duplication. Further, according to an embodiment ofthe disclosure, it is possible to effectively perform duplicatetransmission in a communication environment having multiple links.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a radio bearer structure in an LTE CA environment.

FIG. 2 illustrates a basic flowchart of a transmitter for performingpacket duplication according to an embodiment of the disclosure.

FIG. 3 illustrates a bearer structure for packet duplication accordingto an embodiment of the disclosure.

FIG. 4 illustrates a bearer structure for packet duplication accordingto another embodiment of the disclosure.

FIG. 5 illustrates a bearer structure for packet duplication accordingto another embodiment of the disclosure.

FIG. 6 illustrates a bearer structure for packet duplication accordingto another embodiment of the disclosure.

FIG. 7 illustrates a bearer structure for packet duplication accordingto another embodiment of the disclosure.

FIG. 8 illustrates a bearer structure for packet duplication accordingto another embodiment of the disclosure.

FIG. 9 illustrates a radio bearer configuration message for packetduplication according to an embodiment of the disclosure.

FIG. 10 illustrates configuration and release of packet duplicationaccording to an embodiment of the disclosure.

FIG. 11 illustrates configuration and release of packet duplicationaccording to another embodiment of the disclosure.

FIG. 12 illustrates configuration and release of packet duplicationaccording to another embodiment of the disclosure.

FIG. 13 illustrates a scheme of starting packet transmission through alogical channel for packet duplication when packet duplication isstarted according to an embodiment of the disclosure.

FIG. 14 illustrates a scheme of starting packet transmission through alogical channel for packet duplication when packet duplication isstarted according to another embodiment of the disclosure.

FIG. 15 illustrates a scheme of starting packet transmission through alogical channel for packet duplication when packet duplication isstarted according to another embodiment of the disclosure.

FIG. 16 illustrates a procedure performed when packet duplication isreleased according to an embodiment of the disclosure.

FIG. 17 illustrates a procedure performed when packet duplication isreleased according to another embodiment of the disclosure.

FIG. 18 illustrates an example of a detailed operation when packetduplication is performed.

FIG. 19 illustrates transmission of an uplink buffer status report whenpacket duplication is performed according to an embodiment of thedisclosure.

FIG. 20 illustrates transmission of an uplink buffer status report whenpacket duplication is performed according to another embodiment of thedisclosure.

FIG. 21 illustrates transmission of an uplink buffer status report whenpacket duplication is performed according to another embodiment of thedisclosure.

FIG. 22 illustrates application of the number of times of packetduplication according to an embodiment of the disclosure.

FIG. 23 illustrates a format of a packet duplication activation messageaccording to an embodiment of the disclosure.

FIG. 24 illustrates another format of a packet duplication activationmessage according to an embodiment of the disclosure.

FIG. 25 illustrates another format of a packet duplication activationmessage according to an embodiment of the disclosure.

FIG. 26 illustrates a format of a packet duplication deactivationmessage according to an embodiment of the disclosure.

FIG. 27 illustrates another format of a packet duplication deactivationmessage according to an embodiment of the disclosure.

FIG. 28 illustrates another format of a packet duplication deactivationmessage according to an embodiment of the disclosure.

FIG. 29 illustrates another format of a packet duplicationactivation/deactivation message according to an embodiment of thedisclosure.

FIG. 30 illustrates a radio bearer configuration message for packetduplication according to another embodiment of the disclosure.

FIG. 31 illustrates a radio bearer configuration message for packetduplication according to still another embodiment of the disclosure.

FIG. 32 illustrates another format of a packet duplication activationmessage according to an embodiment of the disclosure.

FIG. 33 illustrates another format of a packet duplication deactivationmessage according to an embodiment of the disclosure.

FIG. 34 illustrates another format of a packet duplication activationmessage according to an embodiment of the disclosure.

FIG. 35 illustrates another format of a packet duplication deactivationmessage according to an embodiment of the disclosure.

FIG. 36 illustrates a format of a message for dynamically changing amapping relationship between a logical channel and a CC according to anembodiment of the disclosure.

FIG. 37 illustrates a procedure of starting configuration of packetduplication according to an embodiment of the disclosure.

FIG. 38 illustrates a terminal according to an embodiment of thedisclosure.

FIG. 39 illustrates a base station according to an embodiment of thedisclosure.

FIG. 40 illustrates determination of a bearer structure and a primarylogical channel for packet duplication according to an embodiment of thedisclosure.

FIG. 41 illustrates an operation of a receiver according to anembodiment of the disclosure.

FIG. 42 illustrates a format of a subheader according to an embodimentof the disclosure.

FIG. 43 illustrates an operation of a receiver according to anembodiment of the disclosure.

DETAILED DESCRIPTION

Hereinafter, exemplary embodiments of the disclosure will be describedin detail with reference to the accompanying drawings. Here, it is notedthat identical reference numerals denote the same structural elements inthe accompanying drawings. Further, a detailed description of a knownfunction and configuration which may make the subject matter of thedisclosure unclear will be omitted.

In describing the exemplary embodiments of the disclosure, descriptionsrelated to technical contents which are well-known in the art to whichthe disclosure pertains, and are not directly associated with thedisclosure, will be omitted. Such an omission of unnecessarydescriptions is intended to prevent obscuring of the main idea of thedisclosure and more clearly transfer the main idea.

For the same reason, in the accompanying drawings, some elements may beexaggerated, omitted, or schematically illustrated. Further, the size ofeach element does not entirely reflect the actual size. In the drawings,identical or corresponding elements are provided with identicalreference numerals.

The advantages and features of the disclosure and ways to achieve themwill be apparent by making reference to embodiments as described belowin detail in conjunction with the accompanying drawings. However, thedisclosure is not limited to the embodiments set forth below, but may beimplemented in various different forms. The following embodiments areprovided only to completely disclose the disclosure and inform thoseskilled in the art of the scope of the disclosure, and the disclosure isdefined only by the scope of the appended claims. Throughout thespecification, the same or like reference numerals designate the same orlike elements.

Here, it will be understood that each block of the flowchartillustrations, and combinations of blocks in the flowchartillustrations, can be implemented by computer program instructions.These computer program instructions can be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which are executed via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions specified in the flowchart block or blocks.These computer program instructions may also be stored in a computerusable or computer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer usable orcomputer-readable memory produce an article of manufacture includinginstruction means that implement the function specified in the flowchartblock or blocks. The computer program instructions may also be loadedonto a computer or other programmable data processing apparatus to causea series of operations to be performed on the computer or otherprogrammable apparatus to produce a computer implemented process suchthat the instructions that execute on the computer or other programmableapparatus provide operations for implementing the functions specified inthe flowchart block or blocks.

In addition, each block of the flowchart illustrations may represent amodule, segment, or portion of code, which includes one or moreexecutable instructions for implementing the specified logicalfunction(s). It should also be noted that in some alternativeimplementations, the functions noted in the blocks may occur out oforder. For example, two blocks shown in succession may in fact beexecuted substantially concurrently or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved.

As used herein, the “unit” refers to a software element or a hardwareelement, such as a Field Programmable Gate Array (FPGA) or anApplication Specific Integrated Circuit (ASIC), which performs apredetermined function. However, the “unit does not always have ameaning limited to software or hardware. The “unit” may be constructedeither to be stored in an addressable storage medium or to execute oneor more processors. Therefore, the “unit” includes, for example,software elements, object-oriented software elements, class elements ortask elements, processes, functions, properties, procedures,sub-routines, segments of a program code, drivers, firmware,micro-codes, circuits, data, database, data structures, tables, arrays,and parameters. The elements and functions provided by the “unit” may beeither combined into a smaller number of elements, “unit” or dividedinto a larger number of elements, “unit”. Moreover, the elements and“units” may be implemented to reproduce one or more CPUs within a deviceor a security multimedia card.

FIG. 1 illustrates a radio bearer structure 100 in an LTE carrieraggregation (CA) environment. In LTE CA, data flow is processed for eachbearer and data is mapped to one radio bearer. These radio bearers aremapped to logical channels on a one-to-one basis and these logicalchannels are multiplexed in a MAC layer and then transmitted. CA is atechnology that uses a collection of various frequency resources bybundling various component carriers (CCs), wherein data having beenmultiplexed in the MAC layer is transmitted through one of CCs. FIG. 1illustrates an embodiment in which radio bearers 1 and 2 each having aPDCP apparatus and an RLC device are mapped to logical channels #1 and#2, respectively. After these logical channels #1 and #2 are multiplexedin the MAC layer, and data is then transmitted through one of CCs 1, 2,and 3. Each logical channel or each radio bearer has no restriction inthe number of CCs available for transmission therefor. Here, the CC maybe recognized as one cell by a terminal, and may be configured as aprimary cell (PCell) or secondary cell (SCell), and the same applies tothe following description.

FIG. 2 illustrates a basic flowchart 200 of a transmitter for performingpacket duplication. When packet duplication is configured for a specificradio bearer 210, data processed by the radio bearer may perform apacket duplication procedure. Generally, the packet duplicationprocedure includes performing a process of data duplication and thentransmitting the data through different logical channels. Here, datapackets copied through packet duplication may be transmitted throughdifferent logical channels 220 and 230 respectively, transmitted todifferent splits in a split bearer environment respectively, transmittedthrough different CCs respectively, or transmitted in differentnumerologies or TTI types. An operation of copying a data packet throughpacket duplication is done by one of the PDCP, RLC, and MAC layers,which are data processing layers. Further, data used herein may be inthe form of an IP packet processed by a user. In some embodiments, thedata may be a control signal within a protocol, such as an RRC message.

FIG. 3 illustrates an embodiment of a bearer structure 300 for packetduplication. In the embodiment illustrated in FIG. 3 , the bearerstructure includes radio bearer A 310 and radio bearer B 320. Generally,one or more signaling radio bearers (SRB) and data radio bearers may beprovided between a base station and a terminal. The radio bearer A 310is a bearer for which packet duplication is allowed, and radio bearer B320 is a bearer for which packet duplication is not allowed. In theembodiment illustrated in FIG. 3 , a process is shown such that a PDCPapparatus (or, entity) of radio bearer A 310 copies a PDCP protocol dataunit (PDU), and transmits the copied PDCP PDUs to different RLC devices,respectively. RLC apparatuses are mapped to logical channels #1 and #2(330 and 340), respectively. Radio bearer B 320 is mapped to one logicalchannel (logical channel #3) because packet duplication thereof is notallowed.

Here, in order to perform efficient packet transmission, mapping of alogical channel to a component carrier (CC) is required. In other words,by mapping a logical channel to a CC (that is, by establishing/defininga mapping relationship between a logical channel and a CC), it ispossible to specify a limit for a CC that can transmit specific logicalchannel data. In a case of packet duplication, the main purpose thereofis to increase reliability and reduce latency by performing separatedata processing of the copied packet and then transmitting the same. Inorder to effectively achieve this purpose, it is required that thecopied data packets are transmitted through different CCs, respectively.In the embodiment illustrated in FIG. 3 , logical channel #1 330 ismapped to CC1 and CC2 so that a data packet of logical channel #1 330may be transmitted through CC1 and CC2, and logical channel #2 340 ismapped to CC3 so that a data packet of logical channel #2 340 may betransmitted through CC3 and the data packet of logical channel #3 may betransmitted through CC2 and CC3. Since a logical channel and a CC aremapped to each other as described above, even if data packets havingbeen copied through packet duplication are subjected to a multiplexingprocess in the MAC apparatus (entity), it is possible to prevent thedata packets from being transmitted through the same CC. In other words,two or more copied data packets are not included in the same MAC PDU,and the original PDCP PDU and the copied PDCP PDU are not transmitted inthe same transmission block.

On the other hand, unlike the above-described embodiment, it is alsopossible to map a logical channel to Numerology or TTI. That is,independently of or in combination with mapping of a logical channel toa CC, it is also possible to map a logical channel to a specificNumerology and/or TTI for data packet transmission. In addition, such amapping between a logical channel and a CC is not limited to the packetduplication process described above, and may be performed separatelyfrom the packet duplication.

Whether or not the bearer allows packet duplication may be determinedaccording to the type of traffic the packet contains. The types oftraffic may be classified into voice, video streaming, web surfing data,and the like, and by such a classification, a specific type of trafficmay be configured to allow packet duplication. Whether to perform packetduplication may also be configured according to a QoS configurationvalue of data. On the other hand, such QoS configuration value may berepresented by an ID indicating QoS such as a QoS flow ID. In this case,it is also possible to allow packet duplication for a specific QoS flowID. For example, a bearer to which a packet having a QoS flow ID havinga value from 0 to 15 is transmitted may perform packet duplication, anda bearer to which a packet having a remaining QoS flow ID is transmittedmay not perform packet duplication. Whether the bearer allows packetduplication may be determined by each of the above-mentioned variouscriteria or a combination of two or more thereof, and other criteriaother than the above-mentioned criteria may be applied.

In addition, packet duplication may be applied to both SRBs thattransmit a control signal and DRBs that transmit data.

FIG. 4 illustrates another embodiment of a bearer structure for packetduplication (as indicated by reference numeral 400). In the embodimentillustrated in FIG. 4 , a radio bearer A 410 and a radio bearer B 420are configured. Generally, one or more signaling radio bearers (SRBs)and data radio bearers may be provided between a base station and aterminal. Radio bearer A 410 is a bearer for which packet duplication isallowed, and radio bearer B 420 is a bearer for which packet duplicationis not allowed. In the embodiment illustrated in FIG. 3 , a process isshown such that an RLC apparatus (or, entity) of radio bearer A 410copies an RLC protocol data unit (PDU), and transmits the copied RLCPDUs through different logical channels, respectively. The RLC apparatusof radio bearer A 410 is mapped to logical channels #1 and #2. Sincepacket duplication in radio bearer B is not allowed, one logical channelis mapped to one logical channel #3.

Here, in order to perform efficient packet transmission, mapping of alogical channel to a component carrier (CC) is required. In other words,by mapping a logical channel to a CC (that is, by establishing/defininga mapping relationship between a logical channel and a CC), it ispossible to specify a limit for a CC that can transmit specific logicalchannel data. In a case of packet duplication, the main purpose thereofis to increase reliability and reduce latency by performing separatedata processing of the copied packet and then transmitting the same. Inorder to effectively achieve this purpose, it is required that thecopied data packets are transmitted through different CCs, respectively.In the embodiment illustrated in FIG. 4 , logical channel #1 is mappedto CC1 and CC2 so that data packets of logical channel #1 may betransmitted through CC1 and CC2, logical channel #2 is mapped to CC3 sothat data packets of logical channel #2 are transmitted through CC3, andthe data packet of logical channel #3 may be transmitted through CC2 andCC3. Since a logical channel and a CC are mapped as described above,even if the data packets having been copied through packet duplicationare subjected to a multiplexing process in the MAC apparatus (entity),it is possible to prevent the data packets from being transmittedthrough the same CC. In other words, two or more copied data packets arenot included in the same MAC PDU, and the original PDCP PDU and thecopied PDCP PDU are not transmitted in the same transmission block.

On the other hand, unlike the above-described embodiment, it is alsopossible to map a logical channel to Numerology or TTI. That is,independently of or in combination with mapping of a logical channel toa CC, it is also possible to map a logical channel to a specificNumerology and/or TTI for data packet transmission. Also, such a mappingbetween a logical channel and a CC is not limited to the packetduplication process described above, and may be performed separatelyfrom the packet duplication.

In addition, packet duplication may be applied to both SRBs thattransmit control signals and DRBs that transmit data.

FIG. 5 illustrates another embodiment of a bearer structure for packetduplication (as indicated by reference numeral 500). For the efficiencyof a communication network, packet duplication may be required to beperformed in a predefined specific situation. To this end, logicalchannels may be classified into and defined as a logical channel(primary logical channel) used both when not performing packetduplication and when performing packet duplication, and a logicalchannel (secondary logical channel) used in data transmission whenperforming packet duplication only. In the embodiment illustrated inFIG. 5 , with regard to radio bearer A 510 that allows packetduplication, logical channel #1 520 is configured as a primary logicalchannel, and logical channel #2 530 is configured as a secondary logicalchannel. The other bearer structure is the same as that defined in FIG.3 . The primary and secondary logical channels may be designated, by abase station, through the RRC configuration, or the like. In addition,the terminal may be notified that data is transmitted on the secondarylogical channel, through a packet duplication activation message, or thelike. A specific embodiment of such a packet duplication activationmessage will be described later.

In addition, packet duplication may be applied to both SRBs thattransmit control signals and DRBs that transmit data.

FIG. 6 illustrates another embodiment of a bearer structure for packetduplication (as indicated by reference numeral 600). For the efficiencyof a communication network, packet duplication may be required to beperformed in a predefined specific situation. To this end, logicalchannels may be classified into and defined as a logical channel(primary logical channel) used both when not performing packetduplication and when performing packet duplication, and a logicalchannel (secondary logical channel) used in data transmission whenperforming packet duplication only. In the embodiment illustrated inFIG. 6 , with regard to radio bearer A 610 that allows packetduplication, logical channel #1 620 is configured as a primary logicalchannel, and logical channel #2 630 is configured as a secondary logicalchannel. The other bearer structure is the same as that defined in FIG.4 . The primary and secondary logical channels may be designated by abase station, through the RRC configuration, or the like. In addition,the terminal may be notified that data is transmitted through thesecondary logical channel, through a packet duplication activationmessage, or the like. A specific embodiment of such a packet duplicationactivation message will be described later.

In addition, packet duplication may be applied to both SRBs thattransmit control signals and DRBs that transmit data.

FIG. 7 illustrates still another embodiment of a bearer structure forpacket duplication (as indicated by reference numeral 700). FIG. 7 showsa simplified structure in which a single radio bearer shown in theembodiments of FIGS. 3 to 6 is mapped to multiple logical channels andCCs, and a PDCP apparatus and an RLC apparatus are omitted therein. ThePDCP apparatus and RLC apparatus may be implemented using one of mappingmethods of the embodiment illustrated in FIGS. 3 to 6 . In theembodiment illustrated in FIG. 7 , radio bearer #1 710 for which packetduplication has been performed is transmitted through logical channels#1 and #3 720 and 750, in which logical channel #1 720 is mapped to CC1730 and CC3 740 and then transmitted therethrough, and logical channel#3 750 is mapped to CC4 760 and CC5 770 and then transmittedtherethrough.

In addition, packet duplication may be applied to both SRBs thattransmit control signals and DRBs that transmit data.

FIG. 8 illustrates another embodiment of a bearer structure for packetduplication (as indicated by reference numeral 800). FIG. 8 shows asimplified structure in which a single radio bearer shown in theembodiments of FIGS. 3 to 6 is mapped to multiple logical channels andCCs, and a PDCP apparatus and an RLC apparatus are omitted therein. ThePDCP apparatus and RLC apparatus may be implemented using one of mappingmethods of the embodiment illustrated in FIGS. 3 to 6 . In theembodiment illustrated in FIG. 8 , a radio bearer #1 810 for whichpacket duplication is performed is transmitted through logical channels#1 and #3 820 and 850, in which logical channel #1 820 is mapped to CC1830 and CC3 840 and then transmitted therethrough, and logical channel#3 850 is mapped to CC4 860 and CC5 870 and then transmittedtherethrough. In the embodiment illustrated in FIG. 8 , it isadditionally shown that each CC supports multiple Numerologies or TTItypes. For example, type 1 of CC1 830 may have a subcarrier spacing of15 KHz and 1 ms TTI, and type 2 835 may have a subcarrier spacing of 30KHz and a 0.25 ms TTI. In the embodiment illustrated in FIG. 8 , radiobearer #1 810 for which packet duplication is performed may betransmitted through type 2 (835) of CC1 830, types 1 and 2 (845) of CC3840, types 1, 2, and 3 (865) of CC4 (860), and type 1 (875) of CC5(870). The above description may be understood such that a specificNumerology and/or TTI type has been previously mapped to a logicalchannel and/or a CC through which copied data packets obtained byperforming packet duplication are transmitted. On the other hand, themapping described above is an embodiment and may be differentlydesignated according to the configuration of a base station or aterminal, the type of traffic, QoS flow ID, and the like.

In addition, packet duplication may be applied to both SRBs thattransmit control signals and DRBs that transmit data.

FIG. 9 illustrates an embodiment of a radio bearer configuration messagefor packet duplication described in FIG. 3 to FIG. 8 (as indicated byreference numeral 900). A DRB ID configured in FIG. 9 is 6 and aDuplicationMode field is configured as true, so that it may be indicatedthat packet duplication is allowed. FIG. 9 shows that a logical channelID (indicated as a LogicalChannelIdentity field) that performs packetduplication is 4 and 5, and a packet transmitted through logical channel#4 may be transmitted only in 15 KHz and 30 KHz Numerologies (asindicated by a Correspondingnumerology field) of CCs 1, 2, and 3, and apacket transmitted through logical channel #5 may use all the CCs and betransmitted only in a 15 kHz Numerology thereamong. The Numerology maybe displayed in frequency intervals as shown in FIG. 9 , but may also bedesignated as a previously configured Numerology or TTI type. Logicalchannel #4 thereamong is a primary logical channel and logical channel#5 is a secondary logical channel (as indicated by a DuplicationTypefield). In addition, each logical channel may independently performduplicate transmission of the same packet, and independently performduplicate packet transmission as many times as the value configured inthe NumberOfDuplication field. Independent duplicate packet transmissionmeans that a transmitter determines to perform the transmission oncemore without receiving NACK of an ARQ.

FIG. 10 illustrates an embodiment for performing configuration andrelease of packet duplication (as indicated by reference numeral 1000).A base station may configure packet duplication of a radio bearer bytransmitting a duplication configuration message to a terminal (S1010).The message may include some of the configuration messages of FIG. 9 .In the embodiment illustrated in FIG. 10 , when the duplicationconfiguration message is received, a terminal configures a bearer forpacket duplication and performs packet duplication (S1020). After that,when the terminal receives a duplication release message from a basestation (S1030), the terminal may release the bearer for packetduplication, release the secondary logical channel for packetduplication, or perform a process of not performing packet duplication(S1040).

FIG. 11 illustrates another embodiment for performing configuration andrelease of packet duplication (as indicated by reference numeral 1100).A base station may configure packet duplication of a radio bearer bytransmitting a duplication configuration message to a terminal (S1110).The message may include some of the configuration messages of FIG. 9 .In the embodiment illustrated in FIG. 11 , when the duplicationconfiguration message is received, a terminal configures a bearer forpacket duplication. After that, when receiving a duplication activationmessage (S1120), the terminal performs actual packet duplication(S1130). Before a duplication activation message is received, a logicalchannel for packet duplication is generated but no actual data istransmitted through a logical channel. At this time, data transmissionthrough a primary logical channel only may be performed. After that,when receiving the duplication deactivation message from a base station(S1140), the terminal stops actual packet duplication (S1150). However,at this time, a bearer structure, such as a logical channel for packetduplication, is not changed. If there is a secondary logical channel,data transmission through the secondary logical channel may be stopped.After that, when a base station receives a duplication release messagefrom a base station (S1160), the terminal may release a bearer forpacket duplication or release a secondary logical channel for packetduplication, or perform a procedure of not performing packetduplication.

FIG. 12 illustrates another embodiment for performing configuration andrelease of packet duplication (as indicated by reference numeral 1200).A base station may configure packet duplication of a radio bearer bytransmitting a duplication configuration message to a terminal (S1210).The message may include some of the configuration messages of FIG. 9 .In the embodiment illustrated in FIG. 12 , when the duplicationconfiguration message is received, the terminal configures a bearer forpacket duplication. After that, when a terminal receives a duplicationactivation message (S1220) and a previously configured condition forpacket duplication (duplication condition) is satisfied (S1230), theterminal performs actual packet duplication (S1240). The condition forpacket duplication may be such that the radio link quality of a terminaland a base station is equal to or lower than a certain level. Before aduplication activation message is received, a logical channel for packetduplication is generated but no actual data is transmitted through thelogical channel. At this time, data transmission through the primarylogical channel only may be performed. If a previously configuredcondition for packet duplication is no longer satisfied or a conditionfor cancellation of packet duplicate transmission is satisfied, packetduplication may not be performed even after reception of the duplicationactivation message. Further, when receiving a duplication deactivationmessage from the base station (S1250), the terminal stops actual packetduplication (S1260). However, at this time, a bearer structure such as alogical channel for packet duplication is not changed. If there is asecondary logical channel, data transmission through the secondarylogical channel may be stopped. After that, when the terminal receives aduplication release message from the base station (S1270), the terminalmay release a bearer for packet duplication, release a secondary logicalchannel for packet duplication, or perform a procedure of not performingpacket duplication.

FIG. 13 illustrates an embodiment of a scheme of starting packettransmission through a logical channel for packet duplication whenpacket duplication is started (as indicated by reference numeral 1300).In the embodiment illustrated in FIG. 13 , it is assumed thattransmission through logical channel #1 (LC1, 1310) only is performedbefore duplicate transmission, and when packet duplication is started,transmission is also performed through logical channel #2 (LC2, 1320).Packet duplication may be performed on the basis of a time point atwhich actual packet duplication begins according to various embodimentsillustrated and described in FIG. 10 to FIG. 12 . In the embodimentillustrated in FIG. 13 , when packet duplication has been started,packets, which have been transmitted from existing logical channel #11310 but no ACK for the packets has been received yet, may betransferred (that is, copied) from the buffer through logical channel #21320 in the sequence from a packet having the earliest sequence number(SN). In the embodiment illustrated in FIG. 13 , even when packets A toE have been transmitted, since only packets A, C, and E are in thereception state at the packet duplication start time, all packets (thatis, B to E) starting from packet B, which has the earliest sequencenumber among packets B and D which have not received ACK, aretransferred (that is, copied) through logical channel #2 1320 so as toperform packet transmission.

In this case, the RLC sequence number (SN) of logical channel #2 1320may be started from the beginning, otherwise the sequence number of theRLC apparatus of logical channel #1 1320 may be used as it is. If thesame sequence numbers are used for logical channel #1 1310 and logicalchannel #2 1320, a part of the RLC state information of logical channel#1 1310 may be transmitted to an RLC apparatus corresponding to logicalchannel #2 1320 of a receiver. Here, the corresponding information mayinclude the start of the RLC SN where transmission begins (RLC SN ofpacket B), all RLC variables, or the like. In addition, thecorresponding information may be PDCP SN or PDCP COUNT corresponding toeach RLC packet according to the embodiment.

FIG. 14 illustrates another embodiment of a scheme of starting packettransmission through a logical channel for packet duplication whenpacket duplication is started (as indicated by reference numeral 1400).In the embodiment illustrated in FIG. 14 , it is assumed thattransmission through logical channel #1 (LC1, 1410) only is performedbefore duplicate transmission, and when packet duplication is started,transmission is also performed through logical channel #2 (LC2, 1420).Packet duplication may be performed on the basis of a time point atwhich actual packet duplication begins according to various embodimentsillustrated and described in FIG. 10 to FIG. 12 . In the embodimentillustrated in FIG. 14 , when packet duplication is started, packetshaving been transmitted through existing logical channel #1 1410 but nothaving received ACK, and packets that have not been transmitted andremain in the buffer may be transferred (that is, copied) throughlogical channel #2 1420 in the sequence starting from the packet havingthe earliest sequence number (SN). In the embodiment illustrated in FIG.14 , even if packets A to E have been transmitted, since only packets A,C, and E are in the reception state at the packet duplication starttime, packets B and D which have not received ACK may be transferred(that is, copied) through logical channel #2 1420, so as to performpacket transmission thereof. If all packets have received ACK, theremaining packets in the buffer may be copied and transmitted throughlogical channel #2 1420.

In this case, the RLC sequence number (SN) of logical channel #2 1420may start from the beginning, or may use the sequence number of the RLCapparatus of logical channel #1 1410 as it is. If the same sequencenumbers are used for logical channel #1 1410 and logical channel #21420, a part of the RLC state information of logical channel #1 1410 maybe transmitted to the RLC apparatus corresponding to logical channel #21420 of a receiver. Here, the corresponding information may include thestart of the RLC SN where transmission begins (RLC SN of packet B) orall RLC variables, and the like. In addition, the correspondinginformation may be PDCP SN or PDCP COUNT corresponding to each RLCpacket according to the embodiment.

FIG. 15 illustrates another embodiment of a scheme of starting packettransmission through a logical channel for packet duplication whenpacket duplication is started (as indicated by reference numeral 1500).In the embodiment illustrated in FIG. 15 , it is assumed thattransmission through logical channel #1 (LC1, 1510) only is performedbefore duplicate transmission and, when packet duplication is started,transmission is also performed through logical channel #2 (LC2, 1520).Packet duplication may be performed on the basis of a time point atwhich actual packet duplication begins according to various embodimentsillustrated and described in FIG. 10 to FIG. 12 . In the embodimentillustrated in FIG. 15 , when packet duplication is started, a packethaving the earliest sequence number (SN), among packets that have notbeen transmitted from the existing logical channel #1 1510, may betransferred (that is, copied) through logical channel #2 1520. In theembodiment illustrated in FIG. 15 , even if packets A to D have beentransmitted, since only packets A and C are in the reception state atthe packet duplication start time, packet duplication is performed suchthat packet duplication is configured for a packet E, which has not beentransmitted, and then transferred (that is, copied) through logicalchannel #1 1510 and logical channel #2 1520. In other words, a datapacket which logical channel #1 1510 has not transmitted may be copiedand transmitted through logical channel #2 1520.

In this case, the RLC sequence number (SN) of logical channel #2 1520may start from the beginning, or otherwise may use the sequence numberof the RLC apparatus of logical channel #1 1510 as it is. If the samesequence numbers are used for logical channel #1 1510 and logicalchannel #2 1520, a part of the RLC state information of logical channel#1 1510 may be transmitted to the RLC apparatus corresponding to logicalchannel #2 1520 of a receiver. Here, the corresponding information mayinclude the start of the RLC SN (RLC SN of packet B) at whichtransmission begins or all RLC variables, and the like. In addition, thecorresponding information may be PDCP SN or PDCP COUNT corresponding toeach RLC packet according to the embodiment.

FIG. 16 illustrates an embodiment of a procedure performed when packetduplication is released while performing data transmission in a statewhere packet duplication is performed (as indicated by reference numeral1600). In the embodiment illustrated in FIG. 16 , an operation performedat a time of releasing actual packet duplication according to variousembodiments described in FIG. 10 to FIG. 12 while performing packettransmission through packet duplication through logical channels #1 and#2 1610 and 1620 is described. In the embodiment illustrated in FIG. 16, at the moment when packet duplication is released, in logical channel#1 1610, ACK for packets A, C, and E has been received and transmissionof packets B and D has been performed, but ACK for the packets B and Dhas not been received yet, and in logical channel #2 1620, ACK forpackets B and E has been received and transmission of packets A, C, andD has been performed, but ACK for the packets A, C, and D has not beenreceived yet. Here, in order not to perform packet duplication, data isto emptied out of one logical channel among logical channels. In FIG. 16, it is assumed that data is arbitrarily emptied out of logical channel#2 (1620), but a logical channel may be selected according to a specificcondition. Here, the specific condition may be a scheme of continuouslyperforming transmission through a primary logical channel, and emptyingdata out of a secondary logical channel and not performing transmissionthereof.

FIG. 17 illustrates another embodiment of a procedure performed whenpacket duplication is released while performing data transmission in astate where packet duplication has been performed (as indicated byreference numeral 1700). FIG. 17 illustrates an operation performed atthe time of releasing actual packet duplication according to variousembodiments described in the description of FIG. 10 to FIG. 12 whileperforming packet transmission through packet duplication throughlogical channels #1 and #2 (1710 and 1720). In the embodimentillustrated in FIG. 17 , at the moment when packet duplication isreleased, in logical channel #1 1710, ACK for packets A, C and E hasbeen received and transmission of packets B and D has been performed,but ACK for the packets B and D has not been received yet, and inlogical channel #2 1720, ACK for packets B and E has been received andtransmission of packets A, C, and D has been performed, but ACK for thepackets A, C, and D has not been received yet. Here, in order not toperform packet duplication, data is to be emptied out of one logicalchannel among logical channels. In FIG. 17 , it is assumed that data isarbitrarily emptied out of logical channel #2 1720, but a logicalchannel may be selected according to a specific condition. Here, thespecific condition may be a scheme of continuously performingtransmission through a primary logical channel, and emptying data out ofa secondary logical channel and not performing transmission thereof.

However, in case of packet B, since transmission already has beensuccessful, information indicating the transmission success may betransmitted through logical channel #1 1710 before emptying logicalchannel #2 1720, so that unnecessary retransmission can be prevented. Inthe embodiment illustrated in FIG. 17 , the RLC apparatus (or entity) oflogical channel #2 1720 informs the RLC apparatus of logical channel #11710 that packets that have successfully received ACK are packets B andE, and the RLC apparatus of logical channel #1 1710 may update a stateof packet B, which has not received ACK, to a successful reception stateand assume that the packet her B has successfully received ACK. Thetransmission of information described above may be performed in a way ofdirectly informing the RLC sequence number (SN) of a packet transmittedfrom the RLC apparatus of logical channel #2 1720 to the RLC apparatusof logical channel #1 1710, or may be performed such that the RLCapparatus of logical channel #2 1720 informs the PDCP apparatus in aradio bearer of the PDCP sequence number (or RLC SN) of thecorresponding packet so that the PDCP apparatus informs the RLCapparatus in logical channel #1 1710 of the sequence number (RLC or PDCPSN) of the corresponding packet. If the RLC sequence numbers of logicalchannel #1 1710 and logical channel #2 1720 are different for eachpacket, a process of converting such a value may be performed. Here, thePDCP sequence number, the PDCP COUNT value, and the like may be used inthe conversion process. In addition, according to the embodiment, theRLC apparatus of one logical channel may directly inform the RLCapparatus in another logical channel of the PDCP SN or the PDCP COUNTinformation of the packet that has received ACK or NACK of thecorresponding packet.

In the embodiment illustrated in FIG. 17 , when the packet duplicatetransmission is released, the transmission status of each logicalchannel described above, that is, the RLC state information or the ACKreception status is transmitted and reflected to another logicalchannel. However, such an operation is not limited to the time pointwhen the packet duplicate transmission is released, and it is possibleto perform a procedure of notifying of the transmission status betweenlogical channels and reflecting the same therein even in a situationwhere normal packet duplication is performed and transmitted. Thetransmission of such information may be performed in a way of directlyinforming the RLC sequence number (SN) of the packet transmitted fromthe RLC apparatus of logical channel #2 1720 to the RLC apparatus oflogical channel #1 1710, or may be performed such that the RLC apparatusof logical channel #2 1720 informs the PDCP apparatus in a radio bearerof a PDCP sequence number of the corresponding packet so that the PDCPapparatus informs the RLC apparatus in logical channel #1 1710 of thesequence number of the corresponding packet. If the RLC sequence numbersof logical channel #1 1710 and logical channel #2 1720 are different foreach packet, a process of converting such a value may be performed.Here, the PDCP sequence number, the PDCP COUNT value, and the like maybe used in the conversion process. According to the embodiment, atransmission interval may be configured as a preconfigured value so thatthe information transmission process does not occur too frequently. Forexample, the transmission interval may be configured such that thetransmission status of a logical channel is transmitted from one logicalchannel to another logical channel every 10 ms. Further, such anoperation may also be applied to a case where packet duplication isapplied to different HARQ apparatuses in a HARQ situation rather than anARQ situation.

Meanwhile, as described in the embodiments of FIG. 16 and FIG. 17 , whenthe packet duplication is released, with regard to packets that exist inthe PDCP buffer and have not been transferred to a lower layer, such asthe RLC, etc. packet transmission may be continuously performed withoutpacket duplication.

FIG. 18 illustrates a specific operation example when packet duplicationis performed (as indicated by reference numeral 1800). In FIG. 18 , thestatus of PDCP PDU #1 1810, PDCP PDU #2 1820, and PDCP PDU #3 1830 at anarbitrary time point is illustrated as an example. In the case of PDCPPDU #1 1810, a packet having arrived at a PDCP layer of a transmitter istransferred to an RLC layer to allow an RLC header to be added thereto,and then, the same is transmitted to a receiver or transferred to a MAClayer or a lower layer thereunder. In the case of PDCP PDU #2 1820, apacket having arrived at a PDCP layer of a transmitter is transferred toan RLC layer to allow an RLC header to be added thereto, but the same isnot yet transferred to a MAC layer or a lower layer thereunder. PDCP PDU#2 1820 may be generated when a packet is previously generated(pre-processed) before a radio resource of an UL grant is allocated.PDCP PDU #3 1830 may be interpreted as a state in which a packet havingarrived at the PDCP layer of the transmitter does not request processingthereof to a lower layer.

According to an embodiment, when packet duplication is performed,duplicate transmission of packets, which have not been transferred tothe RLC layer among packets having arrived at the PDCP layer of thetransmitter, may be started. In the embodiment illustrated in FIG. 18 ,PDCP PDU #3 1830 corresponds to a packet for duplicate transmission.Duplicated transmission of packets, such as PDCP PDU #1 1810 and PDCPPDU #2 1820, which have already been transferred to the RLC layer maynot be started.

According to another embodiment, when packet duplication is performed,duplicate transmission may be started for: a packet (for example, PDCPPDU #1 1810 of FIG. 18 ) which has been transferred to the RLC layer toallow the RLC header to be added thereto, and then is transferred to aMAC layer or a lower layer thereunder or transmitted thereafter, amongpackets having arrived at the PDCP layer of the transmitter; a packet(for example, PDCP PDU #2 18120 of FIG. 18 ) having arrived at the PDCPlayer of the transmitter and transferred to the RLC layer to allow theRLC header to be added thereto, but has not been transferred to a MAClayer or a lower layer thereunder; and a packet (for example, PDCP PDU#3 18930 of FIG. 18 ) having arrived at the PDCP layer of thetransmitter and not transferred to the RLC layer. To this end, whenduplicate transmission is started, the transmitter may transmit (orreport), to the PDCP layer, information on a packet, which is in a stateof not yet having successfully received acknowledgement, among packetshaving been transferred to the RLC layer. Here, the packet informationtransmitted to the PDCP layer may include PDCP SN and the like. Based onthe information, the transmitter may select packets corresponding to thereceived packet information, and may start packet duplicatetransmission. In order to transmit the packet information, the RLC orPDCP layer may manage the RLC sequence number (SN) of the packets andthe value of the PDCP SN. Based on the management of the RLC or PDCP SN,the PDCP sequence number value of packets which have not beensuccessfully transmitted and exist in the RLC buffer may be known.

FIG. 19 illustrates an embodiment in which a terminal transmits anuplink buffer status report to a base station when packet duplication isperformed (as indicated by reference numeral 1900). In the embodimentillustrated in FIG. 19 , radio bearers 1 and 2 do not perform packetduplication and are mapped to logical channels #1 and #2, respectively.However, it is assumed that packet duplication is configured for a radiobearer #3 and the radio bearer #3 is mapped to logical channel #3 1910and logical channel #4 1920. A buffer status report is performed on thebasis of the buffer status of each logical channel. Therefore, a logicalchannel for which packet duplication is performed at the time point oftransmitting the buffer status report is required to determine whatbuffer status to report.

In the embodiment illustrated in FIG. 19 , for logical channels #1 and#2, packet duplication is not performed and the corresponding bufferstatus is used as it is. However, with regard to logical channels #3 and#4 1910 and 1920, a buffer status of logical channel #3 1910 having thelargest quantity of data (buffer status) in the buffer, among twological channels, is used for reporting (as indicated by referencenumeral 1930). According to an embodiment, before transmitting a bufferstatus report, a certain logical channel may share the RLC stateinformation or the ACK reception situation, which has been described inFIG. 17 , with other logical channels.

FIG. 20 illustrates another embodiment in which a terminal transmits anuplink buffer status report to a base station when performing packetduplication (as indicated by reference numeral 2000). In the embodimentillustrated in FIG. 20 , radio bearers 1 and 2 do not perform packetduplication, and are mapped to logical channels #1 and #2, respectively.However, it is assumed that packet duplication is configured for a radiobearer #3 so that the radio bearer #3 is mapped to logical channel #32010 and logical channel #4 2020. A buffer status report is transmittedbased on the buffer status of each logical channel. Therefore, a logicalchannel for which packet duplication is performed at the time point oftransmitting the buffer status report is required to determine whatbuffer status to report.

In the embodiment illustrated in FIG. 20 , for logical channels #1 and#2, packet duplication is not performed and the corresponding bufferstatus is used as it is. However, with regard to logical channels #3 and#4 2010 and 2020, only the buffer status of logical channel #4 2020which has been configured as a primary logical channel is reported (asindicated by reference numeral 2030). Alternatively, the terminal mayarbitrarily select a logical channel or may inform the base stationwhich logical channel is used for a buffer status report. According toan embodiment, a certain logical channel may share the RLC stateinformation or the ACK reception status, which has been described in thedescription of FIG. 17 , with other logical channels before transmittinga buffer status report.

FIG. 21 illustrates an embodiment in which a terminal transmits a uplinkbuffer status report to a base station when performing packetduplication (as indicated by reference numeral 2100). In the embodimentillustrated in FIG. 21 , radio bearers 1 and 2 do not perform packetduplication and are mapped to logical channels #1 and #2, respectively.However, it is assumed that packet duplication is configured for a radiobearer #3, and the radio bearer #3 is mapped to logical channel #3 2110and logical channel #4 2120. The buffer status report is performed onthe basis of the buffer status of each logical channel. Therefore, it isrequired that a logical channel for which packet duplication isperformed at the time of transmitting the buffer status report isrequired to determine what buffer status to report.

In the embodiment illustrated in FIG. 21 , for logical channels #1 and#2, packet duplication is not performed and the corresponding bufferstatus is used as it is. However, for logical channels #3 and #4 2110and 2120, a buffer status report message is generated using the bufferstatus of each logical channel as it is (as indicated by referencenumeral 2130). According to an embodiment, a certain logical channel mayshare the RLC state information or the ACK reception status, which hasbeen described in the description of FIG. 17 , with other logicalchannels before transmitting a buffer status report.

FIG. 22 illustrates an embodiment to which the number of times of packetduplication is applied when packet duplication is performed (asindicated by reference numeral 2200). Packet duplication may beperformed by applying the NumberOfDuplication having been described inFIG. 9 . The NumberOfDuplication field refers to applying the number (orthe number of times) of packet duplications to a logical channel. Here,since too early transmission after performing packet duplication maylower the efficiency of the packet duplication, transmission is requiredto be performed at an interval. In the embodiment illustrated in FIG. 22, the NumberOfDuplication value is configured as 3, so that at the firsttransmission of a packet, the first transmission may be started with theDuplication Count configured as 3, which is the NumberOfDuplicationvalue (as indicated by reference numeral 2210). Thereafter, the copiedpacket may be transmitted after a previously configured timer value, andthe duplication count may be lowered to 2. Similarly, an operation maybe performed such that a copied packet may be transmitted after apredetermined timer value 2220 so as to lower the Duplication Countto 1. When the Duplication Count is changed to 0, no furthertransmission of a copied packet is performed (as indicated by referencenumeral 2240).

Here, the transmission of the copied packet may be performed throughdifferent logical channels or different HARQ apparatuses.

FIG. 23 illustrates an embodiment related to the format of theduplication activation message having been defined in FIGS. 11 and 12(as indicated by reference numeral 2300). Here, a duplication activationmessage 2310 may be transmitted in a MAC control element (CE) format.Further, an indication that the message is a duplication activationmessage may be included in a logical channel ID (LCID) part of thetransmitted MAC CE. Alternatively, if the message includes an ID fieldin addition to the LCD, an indication that the message is a duplicationactivation message may be included in the ID field. Alternatively, aparticular message may include an indication that the message is aduplication activation message, and such a message may be transmitted ina DCI format.

FIG. 24 illustrates an embodiment related to the format of theduplication activation message having been defined in FIGS. 11 and 12(as indicated by reference numeral 2400). Here, the duplicationactivation message 2410 may be transmitted in a MAC control element (CE)format. Further, an indication that the message is a duplicationactivation message may be included in a logical channel ID (LCID) partof the transmitted MAC CE. Alternatively, if the message includes an IDfield in addition to the LCD, an indication that the message is aduplication activation message may be included in the ID field.Alternatively, a particular message may include an indication that themessage is a duplication activation message. Alternatively, aduplication activation message 2410 may be transmitted by adding the IDof a logical channel that allows packet duplication to a radio bearer.In addition, such a message may also be transmitted in a DCI format.

FIG. 25 illustrates an embodiment related to the format of theduplication activation message having been defined in FIGS. 11 and 12(as indicated by reference numeral 2500). Here, a duplication activationmessage 2510 may be transmitted in a MAC control element (CE) format.Further, an indication that the message is a duplication activationmessage may be included in a logical channel ID (LCID) part of thetransmitted MAC CE. Alternatively, if the message includes an ID fieldin addition to the LCD, an indication that the message is a duplicationactivation message may be included in the ID field. Alternatively, aparticular message may include an indication that the message is aduplication activation message. Alternatively, CC information thatallows packet duplication may be included therein and transmitted to aradio bearer. At this time, packet duplication may be performed in a wayof activating a logical channel enabling transmission through thecorresponding CC (or a logical channel mapped to the corresponding CC).In addition, such a message may also be transmitted in a DCI format.

FIG. 26 illustrates an embodiment related to the format of theduplication deactivation message having been defined in FIGS. 11 and 12(as indicated by reference numeral 2600). Here, a duplicationdeactivation message 2610 may be transmitted in a MAC control element(CE) format. Further, an indication that the message is a duplicationdeactivation message may be included in a logical channel ID (LCID) partof the transmitted MAC CE. Alternatively, if the message includes an IDfield in addition to the LCID, an indication that the message is aduplication deactivation message may be included in the ID field.Alternatively, a particular message may include an indication that themessage is a duplication activation message, and such a message may betransmitted in a DCI format.

FIG. 27 illustrates an embodiment related to the format of theduplication deactivation message having been defined in FIGS. 11 and 12(as indicated by reference numeral 2700). Here, a duplicationdeactivation message 2710 may be transmitted in a MAC control element(CE) format. Further, an indication that the message is a duplicationdeactivation message may be included in a logical channel ID (LCID) partof the transmitted MAC CE. Alternatively, if the message includes an IDfield in addition to the LCID, an indication that the message is aduplication deactivation message may be included in the ID field.Alternatively, a particular message may include an indication that themessage is a duplication deactivation message to a particular message.Further, a duplication deactivation message 2710 may be transmitted in astate where the ID of a logical channel for stopping packet duplicationis added to a radio bearer. In addition, such a message may also betransmitted in a DCI format.

FIG. 28 illustrates an embodiment related to the format of a duplicationdeactivation message having been defined in FIGS. 11 and 12 (indicatedby reference numeral 2800). Here, a duplication deactivation message2810 may be transmitted in a MAC control element (CE) format. Further,an indication that the message is a duplication deactivation message maybe included in a logical channel ID (LCID) part of the transmitted MACCE. Alternatively, if the message includes an ID field in addition tothe LCID, an indication that the message is a duplication deactivationmessage may be included in the ID field. Alternatively, a particularmessage may include an indication that the message is a duplicationdeactivation message. Further, CC information for stopping packetduplication may be included in the message and transmitted to a radiobearer. At this time, packet duplication may be stopped in a way ofdeactivating a logical channel enabling transmission through thecorresponding CC (or a logical channel mapped to the corresponding CC).In addition, such a message may also be transmitted in a DCI format.

FIG. 29 is a diagram illustrating another format of a packet duplicationactivation/deactivation message according to an embodiment of thedisclosure (as indicated by reference numeral 2900). In FIG. 29 , aduplication activation/deactivation message 2910 may be transmitted in aMAC CE format. Further, an indication that the message is a duplicationactivation/deactivation message may be included in a logical channel ID(LCD) part of the transmitted MAC CE. Meanwhile, FIG. 29 illustrates anembodiment in which packet duplication is on-off, or activated ordeactivated on the basis of a duplication index. That is, as illustratedin FIG. 29 , the duplication activation/deactivation message 2910 mayinclude duplication indices of I1, I2, . . . , and I8, and each ofduplication indices may have a value of 1 (activation) or 0(deactivation), and the meaning indicated by values 1 and 0 may beconfigured to the opposite thereof. As described above, packetduplication is activated or deactivated on the basis of the bitmap ofthe duplication index, so that activation/deactivation of packetduplication is enabled with respect to a plurality of radiobearers/logical channels/CCs.

FIG. 30 illustrates a diagram of a radio bearer configuration messagefor packet duplication according to another embodiment of the disclosure(as indicated by reference numeral 3000). In the radio bearerconfiguration message illustrated in FIG. 30 , the duplication index isallocated to each duplication radio bearer. In this case, if theduplication index value described in FIG. 29 is configured as 1 toindicate activation, packet duplication of the corresponding duplicationradio bearer is activated.

FIG. 31 illustrates a diagram of a radio bearer configuration messagefor packet duplication according to another embodiment of the disclosure(as indicated by reference numeral 3100). In the radio bearerconfiguration message illustrated in FIG. 30 , the duplication index isallocated to each logical channel. In this case, if the duplicationindex value described in FIG. 29 is configured as 1 to indicateactivation, packet duplication of the corresponding logical channel isactivated. On the other hand, if the duplication index value isconfigured as 0 to indicate deactivation, packet duplication of thecorresponding logical channel is deactivated.

FIG. 32 illustrates a diagram of another format of a packet duplicationactivation message according to another embodiment of the disclosure (asindicated by reference numeral 3200). Here, a duplication activationmessage 3210 may be transmitted in a MAC control element (CE) format.Further, an indication that the message is a duplication activationmessage may be included in a logical channel ID (LCD) part of thetransmitted MAC CE. Alternatively, if the message includes an ID fieldin addition to the LCD, an indication that the message is a duplicationactivation message may be included in the ID field. Alternatively, aparticular message may include an indication that the message is aduplication activation message. In addition, IDs of radio bearers forwhich packet duplication is allowed may also be individually included inthe duplication activation message, and then transmitted. Here, packetduplication may be performed on a data packet transmitted through thecorresponding radio bearer. In addition, such a message may also betransmitted in a DCI format.

FIG. 33 illustrates a diagram of another format of a packet duplicationdeactivation message according to an embodiment of the disclosure (asindicated by reference numeral 3300). Here, a duplication deactivationmessage 3310 may be transmitted in a MAC control element (CE) format.Further, an indication that the message is a duplication deactivationmessage may be included in a logical channel ID (LCD) part of thetransmitted MAC CE. Alternatively, if the message includes an ID fieldin addition to the LCD, an indication that the message is a duplicationdeactivation message may be included in the ID field. Alternatively, aparticular message may include an indication that the message is aduplication deactivation message. In addition, IDs of radio bearers forwhich packet duplication is stopped may also be individually included inthe duplication deactivation message, and then transmitted. Here, packetduplication may be stopped/discontinued on a data packet transmittedthrough the corresponding radio bearer. In addition, such a message mayalso be transmitted in a DCI format.

FIG. 34 illustrates a diagram of another format of a packet duplicationactivation message according to an embodiment of the disclosure (asindicated by reference numeral 3400). Here, a duplication activationmessage 3410 may be transmitted in a MAC control element (CE) format.Further, an indication that the message is a duplication activationmessage may be included in a logical channel ID (LCID) part of thetransmitted MAC CE. Alternatively, if the message includes an ID fieldin addition to the LCD, an indication that the message is a duplicationactivation message may be included in the ID field. Alternatively, aparticular message may include an indication that the message is aduplication activation message. In addition, the transmitted duplicationactivation message may include a plurality of logical channel IDs and anE field for each logical channel ID. When a specific E field has a valueof 1 (or 0), the logic channel ID corresponding to the corresponding Efield may be added to the next byte. In the present embodiment, a radiobearer ID instead of a plurality of logical channel IDs may be includedin the duplication activation message. In addition, such a message mayalso be transmitted in a DCI format.

FIG. 35 illustrates a diagram of another format of a packet duplicationdeactivation message according to an embodiment of the disclosure (asindicated by reference numeral 3500). Here, a duplication deactivationmessage 3510 may be transmitted in a MAC control element (CE) format.Further, an indication that the message is a duplication deactivationmessage may be included in a logical channel ID (LCD) part of thetransmitted MAC CE. Alternatively, if the message includes an ID fieldin addition to the LCD, an indication that the message is a duplicationdeactivation message may be included in the ID field. Alternatively, aparticular message may include an indication that the message is aduplication deactivation message. In addition, the transmittedduplication deactivation message may include a plurality of logicalchannel IDs and an E field for each logical channel ID. When a specificE field has a value of 1 (or 0), the logic channel ID corresponding tothe corresponding E field may be added to the next byte. In the presentembodiment, a radio bearer ID instead of a plurality of logical channelIDs may be included in the duplication deactivation message. Inaddition, such a message may also be transmitted in a DCI format.

FIG. 36 illustrates a diagram of a format of a message dynamicallychanging a mapping relationship between a logical channel and a CCaccording to an embodiment of the disclosure (as indicated by referencenumeral 3600). Here, a duplication carrier mapping message 3610 may betransmitted in a MAC control element (CE) format. Further, an indicationthat the message is a duplication carrier mapping message may beincluded in a logical channel ID (LCD) part of the transmitted MAC CE.Alternatively, if the message includes an ID field in addition to theLCD, an indication that the message is a duplication carrier mappingmessage may be included in the ID field. Alternatively, a particularmessage may include an indication that the message is a duplicationcarrier mapping message.

Meanwhile, the duplication carrier mapping message 3610 is a message fordynamically changing the mapping between a logical channel in whichpacket duplication is performed and a carrier, and as illustrated inFIG. 36 , the duplication carrier mapping massage may include the Civalue (i=1, 2, 3, . . . ) for each of a plurality of CCs. It isindicated that when the Ci value is 0, the corresponding CC is used in aprimary logical channel, and when the Ci value is 1, the correspondingCC is used in the secondary logical channel. A terminal may changemapping between the logical channel and the CC by receiving theduplication carrier mapping message 3610 of FIG. 36 . However, even ifthe mapping between the logical channel and the CC is changed, anongoing retransmission (e.g., HARQ) operation in a specific logicalchannel may proceed as it is.

FIG. 37 illustrates an embodiment of a procedure in which configurationof packet duplication is started (as indicated by reference numeral3700). In the embodiment illustrated in FIG. 37 , a terminal determineswhether a triggering condition of a measurement report previouslyconfigured is satisfied, and measures a reference signal (RS) or thelike (S3710). Here, if the measured value satisfies the triggeringcondition (S3720), the terminal transmits a measurement report messageto a base station (S3730), and based on this, the base station instructsthe configuration of a radio bearer that performs packet duplication(S3740). Such a configuration may be the message format of FIG. 9 , andsome of the fields included in FIG. 9 may be applied thereto. Uponreception of the message, the terminal and the base station mayconfigure a radio bearer that performs packet duplication (S3750). Theformat of the bearer may be one of the formats described in FIG. 3 toFIG. 8 .

FIG. 38 illustrates a diagram of a terminal according to an embodimentof the disclosure (as indicated by reference numeral 3800).

Referring to FIG. 38 , the terminal 3800 may include a transceiver 3810and a controller 3830. The controller 3830 may include at least oneprocessor. The transceiver 3810 and the controller 3830 may beelectrically connected to each other. The controller 3830 may controlthe transceiver 3810 to transmit or receive a signal. The transmissionand/or reception of signals, information, messages, and the like by thecontroller 3830 may be interpreted such that the controller 3830controls the transceiver 3810 so as to transmit and/or receive signals,information, messages, and the like.

The terminal 3800 may transmit and/or receive signals through thetransceiver 3810. The controller 3830 may control the overall operationof the terminal 3800. In addition, the controller 3830 may control theoperation of a terminal having been described through FIG. 1 to FIG. 37.

FIG. 39 illustrates a diagram of a base station according to anembodiment of the disclosure (as indicated by reference numeral 3900).

Referring to FIG. 39 , a base station 3900 may include a transceiver3910 and a controller 3930. The controller 3930 may include at least oneprocessor. The transceiver 3910 and the controller 3930 may beelectrically connected to each other. The controller 3930 may controlthe transceiver 3910 to transmit or receive signals. The transmissionand/or reception of signals, information, messages, and the like by thecontroller 3930 may be interpreted such that the controller 3930controls the transceiver 3910 so as to transmit and/or receive signals,information, messages, and the like.

The base station 3900 may transmit and/or receive signals through thetransceiver 3910. The controller 3930 may control the overall operationof the base station 3900. In addition, the controller 3930 may controlthe operation of a base station having been described through FIG. 1 toFIG. 37 .

FIG. 40 illustrates an embodiment of a bearer structure for packetduplication (as indicated by reference numeral 4000). In the embodimentillustrated in FIG. 40 , one radio bearer is configured to allow packetduplication and a radio bearer ID value is configured as x. Generally,one or more signaling radio bearers (SRB) and data radio bearers may beprovided between a base station and a terminal. In the embodimentillustrated in FIG. 40 , it is illustrated that the PDCP apparatus (or,entity) of a radio bearer copies a PDCP protocol data unit (PDU), andthen transmits the copied PDCP PDUs to different RLC apparatusesrespectively, so as to perform processing thereof. RLC apparatuses aremapped to logical channels, respectively. In the embodiment illustratedin FIG. 40 , each logical channel ID is denoted by y1 4010 and y2 4020.

Here, mapping with a cell is required for efficient packet transmission.In other words, by mapping a logical channel and a cell, it is possibleto specify a limit for a cell that can transmit specific logical channeldata. Such a cell may be replaced by a component carrier (CC), a bandwidth part (BWP), or the like. In the embodiment illustrated in FIG. 40, a logical channel 4010 having logical channel ID y1 is mapped to PCell(or PSCell, or having PSCell for a secondary cell group) and SCell 2,and a logical channel 4020 having logical channel ID y2 is mapped toSCell 3. As described above, a logical channel and a cell are mapped toeach other, so that it is possible to prevent data packets copiedthrough packet duplication from being transmitted to the same cell (orthe same CC, the same BWP) even if the data packets are subjected to amultiplexing process in the MAC apparatus (entity). In other words, twoor more copied data packets are not included in the same MAC PDU, andthe original PDCP PDU and the copied PDCP PDU are not transmitted in thesame transmission block.

Here, with regard to a bearer for which packet duplication is allowed, aprimary logical channel and a secondary logical channel, which have beendescribed in FIGS. 5, 6, 9, 30, 31 , and the like, may be configured.The primary logical channel always transmits/receives packets regardlessof the activation of packet duplication. However, the secondary logicalchannel transmits/receives packets only when packet duplication isactivated. That is, when packet duplication is activated, the same PDCPPDU is transmitted through the primary logical channel and the secondarylogical channel, respectively. Here, the PDCP PDU having beentransmitted through the primary logical channel and the secondarylogical channel may be referred to as an original PDCP PDU and a copiedPDCP PDU, respectively. When packet duplication is deactivated, the PDCPPDU is transmitted through the primary logical channel only. When packetduplication is deactivated, an RLC apparatus of a secondary logicalchannel may be re-established. Whether a specific logical channel is aprimary logical channel or a secondary logical channel may be designatedby a base station, based on the RRC configuration or the like, but it ispossible to define rules for the determination when the configurationthereof is not required. In a packet duplication structure, the primarylogical channel may be determined using one of the following rules.

-   -   A logical channel having a small logical channel ID value is        determined as a primary logical channel. If there are three or        more logical channels, a logical channel having the smallest        logical channel ID is determined as a primary logical channel.        The remaining logical channels are determined as secondary        logical channels.    -   A logical channel having a large logical channel ID is        determined as a primary logical channel. If there are three or        more logical channels, a logical channel having the largest        logical channel ID is determined as a primary logical channel.        The remaining logical channels are determined as secondary        logical channels.    -   A logical channel having a PCell among cells having been mapped        to logical channels is determined as a primary logical channel.        The remaining logical channels are determined as secondary        logical channels.    -   A logical channel having a PCell or a PSCell among the cells        having been mapped to logical channels is determined as a        primary logical channel. The remaining logical channels are        determined as secondary logical channels.    -   A logical channel having a PCell or a PSCell among cells having        been mapped to logical channels is determined as a primary        logical channel. If the primary logical channel is not        determined by the above rules, a logical channel, of which the        minimum SCell index value of an SCell among SCells mapped to the        logical channel is smaller than the minimum SCell index values        of the other logical channels, is determined as the primary        logical channel. The remaining logical channels are determined        as secondary logical channels.    -   A logical channel having a PCell or a PSCell among cells having        been mapped to logical channels is determined as a primary        logical channel. If the primary logical channel is not        determined by the above rules, a logical channel, of which the        maximum SCell index value of an SCell among SCells mapped to the        logical channel is larger than the maximum SCell index values of        the other logical channels, is determined as the primary logical        channel. The remaining logical channels are determined as        secondary logical channels.

FIG. 41 illustrates a procedure of processing when a packetcorresponding to a bearer for which packet duplication is allowed isreceived (as indicated by reference numeral 4100). When a packet isreceived (S4110), if packet duplication is in a state of activation, areceiver transmits the packet to the corresponding logical channel so asto perform processing thereof (S4120, S4130). If packet duplication isin a state of deactivation, the receiver may determine whether thepacket corresponds to primary logical channel (S4120, S4140), and if thepacket is a primary logical channel, the receiver transmits the packetto the corresponding logical channel and performs processing thereof(S4130). Otherwise, the packet may be determined as a packet of asecondary logical channel, and the packet is discarded and is nottransmitted through the logical channel (S4150).

FIG. 42 illustrates a MAC subheader format (as indicated by referencenumeral 4200). The MAC subheader informs of information of a MAC layerdata referred to as a MAC service data unit (SDU). The MAC subheader mayinclude reserved (R), format (F), logical channel ID (LCID), length (L)fields, and the like. The R field is a reserved field and is typicallyconfigured as zero, which is a default value. The F field indicates thelength of the L field. The LCID field indicates the logical channel IDof data (MAC SDU). The L field indicates the length of the MAC SDU.Generally, the above value should be configured as a correct value, andif an unconfigured value (unused value, invalid value) is configured, itmay be considered that there is a packet failure. For example, if the Rfield is configured as 1, it may be processed as an unused value.

FIG. 43 illustrates a procedure of, upon receiving a packet, processingby a receiver (as indicated by reference numeral 4300). FIG. 43illustrates an embodiment in which, upon receiving an MAC PDU, a processis performed by a MAC apparatus (MAC Entity). The received MAC PDU mayinclude a MAC SDU (S4310). Here, the MAC PDU may include at least oneunused value. At this time, an SDU or subheader including thecorresponding value therein may be identified. If the SDU may not becorrectly identified, the entire received MAC PDU may be discarded.Otherwise, if identification of the MAC SDU is enabled, it is checkedwhether an unused value is included in the MAC SDU or the subheader. Ifthere is no unused value, data (SDU) is transmitted through acorresponding logical channel so as to perform processing of packets(S4320, S4330). If an unused value is included, it is required to checkwhether this value corresponds to the LCID field used in the last RRCreconfiguration (reconfiguration immediately before the latest RRCreconfiguration) (S4320, S4340). If, as a result of checking, the LCIDfield has been used for the immediate past RRC reconfiguration, the LCIPfield may be a part generated before the latest RRC reconfiguration andmay not be an error having occurred in the transmission/receptionprocess. In other words, a value used in the immediate pastreconfiguration may be a value that is not used for the latestreconfiguration. In this case, only the corresponding MAC SDU may bediscarded (S4350). This may happen when RRC reconfiguration occurswithout MAC reset or RRC reestablishment. If an unused value is an ID ofa logical channel for which packet duplication is deactivated, theunused value may be data generated when packet duplication is activatedor data transmitted by a transmitter which does not recognizedeactivation thereof. In case where an ID of a logical channel for whichpacket duplication is allowed but is deactivated is included, anoperation of discarding the corresponding MAC SDU only may be performed(S4360, S4350). If an unused value other than those described above isincluded, the entire MAC PDU may be discarded (S4360, S4370).

The embodiments disclosed in the specifications and drawings areprovided merely to readily describe and to help a thorough understandingof the disclosure but are not intended to limit the scope of thedisclosure. Therefore, it should be construed that, in addition to theembodiments disclosed herein, all modifications and changes or modifiedand changed forms derived from the technical idea of the disclosure fallwithin the scope of the disclosure.

What is claimed is:
 1. A method performed by a terminal in a wirelesscommunication system, the method comprising: receiving, from a basestation, first information on a first cell allowed for a first logicalchannel associated with a packet duplication configured for a radiobearer, second information on a first subcarrier spacing (SCS) allowedfor the first logical channel, third information on a second cellallowed for a second logical channel associated with the packetduplication, and fourth information on a second SCS allowed for thesecond logical channel; receiving, from the base station, a first mediumaccess control (MAC) control element (CE) indicating an activation ofthe packet duplication; transmitting, to the base station, a firstuplink data of the first logical channel, wherein the first uplink datais transmitted on the first cell based on the first information by usingthe first SCS based on the second information; and transmitting, to thebase station, a second uplink data of the second logical channel,wherein the second uplink data is transmitted on the second cell basedon the third information by using the second SCS based on the fourthinformation, wherein the second uplink data is a duplicate of the firstuplink data and the second uplink data is duplicated from the firstuplink data based on the first MAC CE.
 2. The method of claim 1,wherein, in case that a successful delivery of a data is confirmed by afirst radio link control (RLC) entity associated with the radio bearer,a packet data convergence protocol (PDCP) entity of the radio bearerindicates the successful delivery of the data to a second RLC entityassociated with the radio bearer.
 3. The method of claim 1, furthercomprising: receiving, from the base station, a second MAC CE indicatinga deactivation of the packet duplication, wherein all duplicated data ina secondary RLC entity for the radio bearer is discarded based on thesecond MAC CE.
 4. The method of claim 1, wherein the first logicalchannel and the second logical channel are associated with one MACentity, and the first cell and the second cell are different cells.
 5. Amethod performed by a base station in a wireless communication system,the method comprising: transmitting, to a terminal, first information ona first cell allowed for a first logical channel associated with apacket duplication configured for a radio bearer, second information ona first subcarrier spacing (SCS) allowed for the first logical channel,third information on a second cell allowed for a second logical channelassociated with the packet duplication, and fourth information on asecond SCS allowed for the second logical channel; transmitting, to theterminal, a first medium access control (MAC) control element, CE,indicating an activation of the packet duplication; receiving, from theterminal, a first uplink data of the first logical channel, wherein thefirst uplink data is received on the first cell based on the firstinformation by using the first SCS based on the second information; andreceiving, from the terminal, a second uplink data of the second logicalchannel, wherein the second uplink data is received on the second cellbased on the third information by using the second SCS based on thefourth information, wherein the second uplink data is a duplicate of thefirst uplink data and the second uplink data is duplicated from thefirst uplink data based on the first MAC CE.
 6. The method of claim 5,wherein, in case that a successful delivery of a data is confirmed by afirst radio link control (RLC) entity associated with the radio bearer,a packet data convergence protocol (PDCP) entity of the radio bearerindicates the successful delivery of the data to a second RLC entityassociated with the radio bearer.
 7. The method of claim 5, furthercomprising: transmitting, to the terminal, a second MAC CE indicating adeactivation of the packet duplication, wherein all duplicated data in asecondary RLC entity for the radio bearer is discarded based on thesecond MAC CE.
 8. The method of claim 5, wherein the first logicalchannel and the second logical channel are associated with one MACentity, and the first cell and the second cell are different cells.
 9. Aterminal in a wireless communication system, the terminal comprising: atransceiver configured to transmit and receive a signal; and acontroller coupled with the transceiver and configured to: receive, froma base station, first information on a first cell allowed for a firstlogical channel associated with a packet duplication configured for aradio bearer, second information on a first subcarrier spacing (SCS)allowed for the first logical channel, third information on a secondcell allowed for a second logical channel associated with the packetduplication, and fourth information on a second SCS allowed for thesecond logical channel, receive, from the base station, a first mediumaccess control (MAC) control element, CE, indicating an activation ofthe packet duplication, transmit, to the base station, a first uplinkdata of the first logical channel, wherein the first uplink data istransmitted on the first cell based on the first information by usingthe first SCS based on the second information, and transmit, to the basestation, a second uplink data of the second logical channel, wherein thesecond uplink data is transmitted on the second cell based on the thirdinformation by using the second SCS based on the fourth information,wherein the second uplink data is a duplicate of the first uplink dataand the second uplink data is duplicated from the first uplink databased on the first MAC CE.
 10. The terminal of claim 9, wherein, in casethat a successful delivery of a data is confirmed by a first radio linkcontrol (RLC) entity associated with the radio bearer, a packet dataconvergence protocol (PDCP) entity of the radio bearer indicates thesuccessful delivery of the data to a second RLC entity associated withthe radio bearer.
 11. The terminal of claim 9, wherein the controller isfurther configured to: receive, from the base station, a second MAC CEindicating a deactivation of the packet duplication, and wherein allduplicated data in a secondary RLC entity for the radio bearer isdiscarded based on the second MAC CE.
 12. The terminal of claim 9,wherein the first logical channel and the second logical channel areassociated with one MAC entity, and the first cell and the second cellare different cells.
 13. A base station in a wireless communicationsystem, the base station comprising: a transceiver configured totransmit and receive a signal; and a controller coupled with thetransceiver and configured to: transmit, to a terminal, firstinformation on a first cell allowed for a first logical channelassociated with a packet duplication configured for a radio bearer,second information on a first subcarrier spacing (SCS) allowed for thefirst logical channel, third information on a second cell allowed for asecond logical channel associated with the packet duplication, andfourth information on a second SCS allowed for the second logicalchannel, transmit, to the terminal, a first medium access control (MAC)control element (CE) indicating an activation of the packet duplication,receive, from the terminal, a first uplink data of the first logicalchannel, wherein the first uplink data is received on the first cellbased on the first information by using the first SCS based on thesecond information, and receive, from the terminal, a second uplink dataof the second logical channel, wherein the second uplink data isreceived on the second cell based on the third information by using thesecond SCS based on the fourth information, wherein the second uplinkdata is a duplicate of the first uplink data and the second uplink datais duplicated from the first uplink data based on the first MAC CE. 14.The base station of claim 13, wherein, in case that a successfuldelivery of a data is confirmed by a first radio link control (RLC)entity associated with the radio bearer, a packet data convergenceprotocol (PDCP) entity of the radio bearer indicates the successfuldelivery of the data to a second RLC entity associated with the radiobearer.
 15. The base station of claim 13, wherein the controller isfurther configured to: transmit, to the terminal, a second MAC CEindicating a deactivation of the packet duplication, and wherein allduplicated data in a secondary RLC entity for the radio bearer isdiscarded based on the second MAC CE.
 16. The base station of claim 13,wherein the first logical channel and the second logical channel areassociated with one MAC entity, and the first cell and the second cellare different cells.